home *** CD-ROM | disk | FTP | other *** search
/ Internet Info 1997 December / Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso / ietf / urn / urn-archives / urn-ietf.archive.9611 / 000203_owner-urn-ietf _Tue Nov 26 10:45:09 1996.msg < prev    next >
Internet Message Format  |  1997-02-19  |  5KB
  1. Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id KAA09376 for urn-ietf-out; Tue, 26 Nov 1996 10:45:09 -0500
  2. Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id KAA09371 for <urn-ietf@services.bunyip.com>; Tue, 26 Nov 1996 10:45:07 -0500
  3. Received: from ietf.org by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
  4.         id AA15902  (mail destined for urn-ietf@services.bunyip.com); Tue, 26 Nov 96 10:45:03 -0500
  5. Received: from ietf.org by ietf.org id aa19547; 26 Nov 96 9:20 EST
  6. Mime-Version: 1.0
  7. Content-Type: Multipart/Mixed; Boundary="NextPart"
  8. To: IETF-Announce:;
  9. Cc: urn-ietf@bunyip.com
  10. From: Internet-Drafts@ietf.org
  11. Subject: [URN] I-D ACTION:draft-ietf-urn-req-frame-00.txt
  12. Date: Tue, 26 Nov 1996 09:20:46 -0500
  13. Message-Id:  <9611260920.aa19547@ietf.org>
  14. Sender: owner-urn-ietf@services.bunyip.com
  15. Precedence: bulk
  16. Reply-To: Internet-Drafts@ietf.org
  17. Errors-To: owner-urn-ietf@bunyip.com
  18.  
  19. --NextPart
  20.  
  21.  A New Internet-Draft is available from the on-line Internet-Drafts 
  22.  directories. This draft is a work item of the Uniform Resource Names 
  23.  Working Group of the IETF.                                                
  24.  
  25.        Title     : Requirements and a Framework for URN Resolution Systems 
  26.        Author(s) : K. Sollins
  27.        Filename  : draft-ietf-urn-req-frame-00.txt
  28.        Pages     : 17
  29.        Date      : 11/25/1996
  30.  
  31. This document addresses the issues of the discovery of local URN resolution
  32. services that in turn will directly translate URNs into URLs and URCs.  The
  33. document falls into three major parts, the assumptions underlying the work,
  34. the requirements in order to be a viable URN-resolution-service discovery 
  35. service or UDS, and a framework for designing UDSs.  The requirements fall 
  36. into three major areas: evolvability, usability, and security and privacy. 
  37. A UDS that is compliant with the framework will not necessarily be 
  38. compliant with the requirements.  Compliance with the requirements will 
  39. need to be validated separately.                                           
  40.  
  41. Internet-Drafts are available by anonymous FTP.  Login with the username
  42. "anonymous" and a password of your e-mail address.  After logging in,
  43. type "cd internet-drafts" and then
  44.      "get draft-ietf-urn-req-frame-00.txt".
  45. A URL for the Internet-Draft is:
  46. ftp://ds.internic.net/internet-drafts/draft-ietf-urn-req-frame-00.txt
  47.  
  48. Internet-Drafts directories are located at:    
  49.                                                     
  50.      o  Africa:  ftp.is.co.za                    
  51.                                                     
  52.      o  Europe:  nic.nordu.net                
  53.                  ftp.nis.garr.it                 
  54.                                                     
  55.      o  Pacific Rim: munnari.oz.au               
  56.                                                     
  57.      o  US East Coast: ds.internic.net           
  58.                                                     
  59.      o  US West Coast: ftp.isi.edu               
  60.                                                     
  61. Internet-Drafts are also available by mail.    
  62.                                                     
  63. Send a message to:  mailserv@ds.internic.net. In the body type: 
  64.      "FILE /internet-drafts/draft-ietf-urn-req-frame-00.txt".
  65.                             
  66. NOTE: The mail server at ds.internic.net can return the document in
  67.       MIME-encoded form by using the "mpack" utility.  To use this
  68.       feature, insert the command "ENCODING mime" before the "FILE"
  69.       command.  To decode the response(s), you will need "munpack" or
  70.       a MIME-compliant mail reader.  Different MIME-compliant mail readers
  71.       exhibit different behavior, especially when dealing with
  72.       "multipart" MIME messages (i.e., documents which have been split
  73.       up into multiple messages), so check your local documentation on
  74.       how to manipulate these messages.
  75.                             
  76.                             
  77.  
  78. Below is the data which will enable a MIME compliant mail reader 
  79. implementation to automatically retrieve the ASCII version
  80. of the Internet-Draft.
  81.  
  82. --NextPart
  83. Content-Type: Multipart/Alternative; Boundary="OtherAccess"
  84.  
  85. --OtherAccess
  86. Content-Type:  Message/External-body;
  87.         access-type="mail-server";
  88.         server="mailserv@ds.internic.net"
  89.  
  90. Content-Type: text/plain
  91. Content-ID: <19961125154650.I-D@ietf.org>
  92.  
  93. ENCODING mime
  94. FILE /internet-drafts/draft-ietf-urn-req-frame-00.txt
  95.  
  96. --OtherAccess
  97. Content-Type:   Message/External-body;
  98.         name="draft-ietf-urn-req-frame-00.txt";
  99.         site="ds.internic.net";
  100.         access-type="anon-ftp";
  101.         directory="internet-drafts"
  102.  
  103. Content-Type: text/plain
  104. Content-ID: <19961125154650.I-D@ietf.org>
  105.  
  106. --OtherAccess--
  107.  
  108. --NextPart--